Network identification of portable electronic devices while changing power states

ABSTRACT

Systems and methods for maintaining knowledge of a network address (e.g., a MAC address) for a playback device while changing power states are disclosed. In one embodiment, a method for maintaining knowledge of the network identity of a playback device while changing power states includes determining that a playback device is entering a sleep state, sending state information from the playback device to a central data repository over a network responsive to the determination that the playback device is entering sleep state, where state information includes a MAC address, receiving the state information about the playback device at a waking device from the central data repository, waking the playback device periodically at predetermined time intervals while in sleep state to listen for messages addressed to the MAC address, and receiving a wake-up message at the playback device from the waking device and responding by changing from sleep to active state.

FIELD OF THE DISCLOSURE

The present disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loud setting were limited until in 2002, when SONOS, Inc. began development of a new type of playback system. Sonos then filed one of its first patent applications in 2003, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering its first media playback systems for sale in 2005. The Sonos Wireless Home Sound System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a controller (e.g., smartphone, tablet, computer, voice input device), one can play what she wants in any room having a networked playback device. Media content (e.g., songs, podcasts, video sound) can be streamed to playback devices such that each room with a playback device can play back corresponding different media content. In addition, rooms can be grouped together for synchronous playback of the same media content, and/or the same media content can be heard in all rooms synchronously.

SUMMARY OF THE INVENTION

Systems and methods for maintaining knowledge of a network address (e.g., a MAC address) for a playback device while the playback device changes power states to a lower power or dormant state in which it is not sending its network address to other devices are disclosed. In one embodiment, a method for maintaining knowledge of the network identity of a network-connected playback device while changing power states includes determining that a playback device is entering a power state of sleep state, sending state information from the playback device to a central data repository over a network when the playback device responsive to the determination that the playback device is entering sleep state, where state information includes a MAC address of the playback device, receiving the state information about the playback device at a waking device from the central data repository, waking the playback device periodically at predetermined time intervals while in sleep state to listen for messages addressed to the MAC address of the playback device, and receiving a wake-up message at the playback device from the waking device and responding by changing from sleep state to active state.

A further embodiment includes maintaining a power state on a playback device, where the power state is in one power state of at least the states of: active, standby, and sleep, broadcasting a MAC address associated with the playback device at a first predetermined time interval when the playback device is in the active power state, broadcasting the MAC address associated with the playback device at a second predetermined time interval when the playback device is in the standby power state, and ceasing broadcasting the MAC address when the playback device enters the sleep state.

Another embodiment includes reducing power to at least one electrical component of the playback device when the playback device transitions from the active power state to the standby power state, and increasing power to the at least one electrical component of the playback device when the playback device transitions from the standby power state to the active power state.

In a still further embodiment, the central data repository is a cloud network.

Still another embodiment includes sending a request for state information from the waking device to the cloud network, where the request for state information includes an identifier of the playback device.

In a yet further embodiment, the playback device is not connected to an external power source.

In yet another embodiment, state information includes status of whether the playback device is in a state that cannot receive or respond to a magic frame.

In a further embodiment again, the wake-up message is unicast addressed to the playback device.

In another embodiment again, the wake-up message is broadcast on a network that the playback device is connected to.

In a further additional embodiment, the controller device is another member of a group acting as group controller requesting MAC addresses of all devices in the group.

In another additional embodiment, the second predetermined time interval is longer than the first predetermined time interval.

In a still yet further embodiment, sending state information from the playback device to a cloud network when the playback device enters the sleep state includes sending state information from the playback device to a cloud network when the playback device enters the sleep state from standby state.

In still yet another embodiment, a method for changing power states of a network-connected playback device using a waking device includes requesting and receiving, by a waking device from a central data repository over a network, state information about at least one playback device, where the state information includes a MAC address associated with each at least one playback device and data indicating that each at least one playback device is in a sleep state, receiving input on a user interface on the waking device causing an instruction to cause the at least one playback device to come out of sleep state, responsive to the input on the user interface causing the instruction to cause the at least one playback device to come out of sleep state, sending a wake up message from the waking device with a magic frame to each MAC address associated with each at least one playback device.

In a still further embodiment again, the input on a user interface on the waking device causing an instruction to cause the at least one playback device to come out of sleep state includes detection of an input selecting the at least one playback device.

In still another embodiment again, the input on a user interface on the waking device causing an instruction to cause the at least one playback device to come out of sleep state includes an instruction to a group controller, where the group controller is a controller for a group of playback devices to which the at least one playback device belongs, to have the group of playback devices play a media content.

In a still further additional embodiment, requesting and receiving, by a waking device from a central data repository over a network, state information about at least one playback device is performed periodically at a predetermined time interval.

In still another additional embodiment, requesting and receiving, by a waking device from a central data repository over a network, state information about at least one playback device is performed in response to an event on the waking device.

In a yet further embodiment again, the event on the waking device includes a controller application being opened on the waking device.

In yet another embodiment again, the event on the waking device includes the waking device connecting to a local network containing the group of playback devices for the first time.

In a yet further additional embodiment, the central data repository is a cloud network.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings, as listed below. A person skilled in the relevant art will understand that the features shown in the drawings are for purposes of illustrations, and variations, including different and/or additional features and arrangements thereof, are possible.

FIG. 1A is a partial cutaway view of an environment having a media playback system configured in accordance with aspects of the disclosed technology.

FIG. 1B is a schematic diagram of the media playback system of FIG. 1A and one or more networks.

FIG. 1C is a block diagram of a playback device in accordance with an embodiment of the invention.

FIG. 1D is a block diagram of a playback device in accordance with an embodiment of the invention.

FIG. 1E is a block diagram of a network microphone device in accordance with an embodiment of the invention.

FIG. 1F is a block diagram of a network microphone device in accordance with an embodiment of the invention.

FIG. 1G is a block diagram of a playback device in accordance with an embodiment of the invention.

FIG. 1H is a partial schematic diagram of a control device in accordance with an embodiment of the invention.

FIGS. 1-I through 1L are schematic diagrams of corresponding media playback system zones in accordance with an embodiment of the invention.

FIG. 1M is a schematic diagram of media playback system areas in accordance with an embodiment of the invention.

FIG. 2A is a front isometric view of a playback device configured in accordance with an embodiment of the invention.

FIG. 2B is a front isometric view of the playback device of FIG. 3A without a grille.

FIG. 2C is an exploded view of the playback device of FIG. 2A.

FIG. 3A is a front view of a network microphone device configured in accordance in accordance with an embodiment of the invention.

FIG. 3B is a side isometric view of the network microphone device of FIG. 3A.

FIG. 3C is an exploded view of the network microphone device of FIGS. 3A and 3B.

FIG. 3D is an enlarged view of a portion of FIG. 3B.

FIG. 3E is a block diagram of the network microphone device of FIGS. 3A-3D in accordance with an embodiment of the invention.

FIG. 3F is a schematic diagram of an example voice input.

FIGS. 4A-4D are schematic diagrams of a control device in various stages of operation in accordance with an embodiment of the invention.

FIG. 5 is front view of a control device in accordance with an embodiment of the invention.

FIG. 6 is a message flow diagram of a media playback system in accordance with an embodiment of the invention.

FIG. 7 conceptually illustrates a playback device in accordance with an embodiment of the invention.

FIG. 8 conceptually illustrates power state transitions of a playback device in accordance with an embodiment of the invention.

FIG. 9 is a flow chart illustrating a process for maintaining state information of a playback device at a central repository in accordance with an embodiment of the invention.

FIG. 10 is a message flow diagram of a media playback system maintaining state information of a playback device across power states in accordance with an embodiment of the invention.

The drawings are for the purpose of illustrating example embodiments, but those of ordinary skill in the art will understand that the technology disclosed herein is not limited to the arrangements and/or instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments described herein relate to maintaining knowledge of a network address (e.g., a MAC address) for a playback device while the playback device changes power states to a lower power or dormant state in which it is not sending its network address to other devices.

Many embodiments of the invention involve at least one networked playback device in a media playback system that may be controlled by another device on the network through a control application installed on a controller device (e.g., smartphone, tablet, computer, voice input device). The playback device may be constant-powered, e.g. by AC power or a wall adapter, or battery-powered, e.g., disconnected from AC power or wall adapter, or capable of both. Whether the playback device is under constant-power or battery-power, it may be in one of several “power states,” each of which is defined by having one or more components in a higher or lower power (or off) mode relative to at least one other state. Different configurations of power states are discussed further below. Power states can include, but are not limited to, an active state in which the playback device is ready play back media content upon receiving an instruction, a standby state where one or more components related to audio reproduction (such as a power amplifier) are in low power mode or off, and/or a sleep state where one or more network components (such as a wireless network interface) are in low power mode or off. In one or more power states, a network on the playback device may be in a mode that does not broadcast its MAC address (or similar unique network address) and/or respond to requests for its MAC address.

A controller device may become disconnected from the network at some time, for example, when a user leaves their home and their smartphone disconnects from the local wireless network. When the controller device reconnects to the network, e.g., when the user returns home, the control application may query playback devices that are available on the local network. In some cases, playback device(s) that are in a power state that does broadcast MAC addresses and does not respond to requests for MAC addresses may potentially not be identified by the controller device as available for playback control. Techniques proposed here address such scenarios.

In some embodiments, for example, a MAC address (or other network address) of a playback device is sent from the playback device to a cloud network upon an event, the MAC address can be sent to a waking device (i.e. a device that is waking the playback device) in response to a request, and the waking device can use the MAC address to send a message to wake the playback device by triggering it to change power state. As discussed further below, events that may trigger the playback device to send its MAC address to a cloud network can be when the playback device changes power states (e.g., goes into sleep or another state that does not broadcast and/or respond to requests for its MAC address). A waking device, such as a controller device or a second playback device, that seeks to communicate with the first playback device may request the MAC address associated with the first playback device, for example, when it generates a display of available playback devices on the network or when it sends a command for playback to the first playback device or a group of devices including the first playback device. Additional embodiments and techniques are described in greater detail further below.

While some examples described herein may refer to functions performed by given actors such as “users,” “listeners,” and/or other entities, it should be understood that this is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.

In the Figures, identical reference numbers identify generally similar, and/or identical, elements. To facilitate the discussion of any particular element, the most significant digit or digits of a reference number refers to the Figure in which that element is first introduced. For example, element 110 a is first introduced and discussed with reference to FIG. 1A. Many of the details, dimensions, angles and other features shown in the Figures are merely illustrative of particular embodiments of the disclosed technology. Accordingly, other embodiments can have other details, dimensions, angles and features without departing from the spirit or scope of the disclosure. In addition, those of ordinary skill in the art will appreciate that further embodiments of the various disclosed technologies can be practiced without several of the details described below.

II. Suitable Operating Environment

FIG. 1A is a partial cutaway view of a media playback system 100 distributed in an environment 101 (e.g., a house). The media playback system 100 comprises one or more playback devices 110 (identified individually as playback devices 110 a-n), one or more network microphone devices 120 (“NMDs”) (identified individually as NMDs 120 a-c), and one or more control devices 130 (identified individually as control devices 130 a and 130 b).

As used herein the term “playback device” can generally refer to a network device configured to receive, process, and output data of a media playback system. For example, a playback device can be a network device that receives and processes audio content. In some embodiments, a playback device includes one or more transducers or speakers powered by one or more amplifiers. In other embodiments, however, a playback device includes one of (or neither of) the speaker and the amplifier. For instance, a playback device can comprise one or more amplifiers configured to drive one or more speakers external to the playback device via a corresponding wire or cable.

Moreover, as used herein the term “NMD” (i.e., a “network microphone device”) can generally refer to a network device that is configured for audio detection. In some embodiments, an NMD is a stand-alone device configured primarily for audio detection. In other embodiments, an NMD is incorporated into a playback device (or vice versa).

The term “control device” can generally refer to a network device configured to perform functions relevant to facilitating user access, control, and/or configuration of the media playback system 100.

Each of the playback devices 110 is configured to receive audio signals or data from one or more media sources (e.g., one or more remote servers, one or more local devices) and play back the received audio signals or data as sound. The one or more NMDs 120 are configured to receive spoken word commands, and the one or more control devices 130 are configured to receive user input. In response to the received spoken word commands and/or user input, the media playback system 100 can play back audio via one or more of the playback devices 110. In certain embodiments, the playback devices 110 are configured to commence playback of media content in response to a trigger. For instance, one or more of the playback devices 110 can be configured to play back a morning playlist upon detection of an associated trigger condition (e.g., presence of a user in a kitchen, detection of a coffee machine operation). In some embodiments, for example, the media playback system 100 is configured to play back audio from a first playback device (e.g., the playback device 100 a) in synchrony with a second playback device (e.g., the playback device 100 b). Interactions between the playback devices 110, NMDs 120, and/or control devices 130 of the media playback system 100 configured in accordance with the various embodiments of the disclosure are described in greater detail below with respect to FIGS. 1B-6.

In the illustrated embodiment of FIG. 1A, the environment 101 comprises a household having several rooms, spaces, and/or playback zones, including (clockwise from upper left) a master bathroom 101 a, a master bedroom 101 b, a second bedroom 101 c, a family room or den 101 d, an office 101 e, a living room 101 f, a dining room 101 g, a kitchen 101 h, and an outdoor patio 101 i. While certain embodiments and examples are described below in the context of a home environment, the technologies described herein may be implemented in other types of environments. In some embodiments, for example, the media playback system 100 can be implemented in one or more commercial settings (e.g., a restaurant, mall, airport, hotel, a retail or other store), one or more vehicles (e.g., a sports utility vehicle, bus, car, a ship, a boat, an airplane), multiple environments (e.g., a combination of home and vehicle environments), and/or another suitable environment where multi-zone audio may be desirable.

The media playback system 100 can comprise one or more playback zones, some of which may correspond to the rooms in the environment 101. The media playback system 100 can be established with one or more playback zones, after which additional zones may be added, or removed, to form, for example, the configuration shown in FIG. 1A. Each zone may be given a name according to a different room or space such as the office 101 e, master bathroom 101 a, master bedroom 101 b, the second bedroom 101 c, kitchen 101 h, dining room 101 g, living room 101 f, and/or the balcony 101 i. In some aspects, a single playback zone may include multiple rooms or spaces. In certain aspects, a single room or space may include multiple playback zones.

In the illustrated embodiment of FIG. 1A, the master bathroom 101 a, the second bedroom 101 c, the office 101 e, the living room 101 f, the dining room 101 g, the kitchen 101 h, and the outdoor patio 101 i each include one playback device 110, and the master bedroom 101 b and the den 101 d include a plurality of playback devices 110. In the master bedroom 101 b, the playback devices 110 l and 110 m may be configured, for example, to play back audio content in synchrony as individual ones of playback devices 110, as a bonded playback zone, as a consolidated playback device, and/or any combination thereof. Similarly, in the den 101 d, the playback devices 110 h-j can be configured, for instance, to play back audio content in synchrony as individual ones of playback devices 110, as one or more bonded playback devices, and/or as one or more consolidated playback devices. Additional details regarding bonded and consolidated playback devices are described below with respect to FIGS. 1B and 1E and 1I-1M.

In some aspects, one or more of the playback zones in the environment 101 may each be playing different audio content. For instance, a user may be grilling on the patio 101 i and listening to hip hop music being played by the playback device 110 c while another user is preparing food in the kitchen 101 h and listening to classical music played by the playback device 110 b. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the office 101 e listening to the playback device 110 f playing back the same hip hop music being played back by playback device 110 c on the patio 101 i. In some aspects, the playback devices 110 c and 110 f play back the hip hop music in synchrony such that the user perceives that the audio content is being played seamlessly (or at least substantially seamlessly) while moving between different playback zones. Additional details regarding audio playback synchronization among playback devices and/or zones can be found, for example, in U.S. Pat. No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is incorporated herein by reference in its entirety.

a. Suitable Media Playback System

FIG. 1B is a schematic diagram of the media playback system 100 and at least one cloud network 102. For ease of illustration, certain devices of the media playback system 100 and the cloud network 102 are omitted from FIG. 1B. One or more communication links 103 (referred to hereinafter as “the links 103”) communicatively couple the media playback system 100 and the cloud network 102.

The links 103 can comprise, for example, one or more wired networks, one or more wireless networks, one or more wide area networks (WAN), one or more local area networks (LAN), one or more personal area networks (PAN), one or more telecommunication networks (e.g., one or more Global System for Mobiles (GSM) networks, Code Division Multiple Access (CDMA) networks, Long-Term Evolution (LTE) networks, 5G communication network networks, and/or other suitable data transmission protocol networks), etc. In many embodiments, a cloud network 102 is configured to deliver media content (e.g., audio content, video content, photographs, social media content) to the media playback system 100 in response to a request transmitted from the media playback system 100 via the links 103. In some embodiments, a cloud network 102 is configured to receive data (e.g., voice input data) from the media playback system 100 and correspondingly transmit commands and/or media content to the media playback system 100. In further embodiments, the cloud network 102 or a different cloud network is configured to receive state information (e.g., MAC address, etc.) from a playback device as described further below and maintain the MAC address to be retrieved by a waking device seeking to wake the playback device (e.g., trigger a power state transition from a lower or dormant power state to a higher power or ready state). The cloud network may maintain a table of playback device identifiers with associated MAC addresses or utilize a similar structure.

The cloud network 102 comprises computing devices 106 (identified separately as a first computing device 106 a, a second computing device 106 b, and a third computing device 106 c). The computing devices 106 can comprise individual computers or servers, such as, for example, a media streaming service server storing audio and/or other media content, a voice service server, a social media server, a media playback system control server, etc. In some embodiments, one or more of the computing devices 106 comprise modules of a single computer or server. In certain embodiments, one or more of the computing devices 106 comprise one or more modules, computers, and/or servers. Moreover, while the cloud network 102 is described above in the context of a single cloud network, in some embodiments the cloud network 102 comprises a plurality of cloud networks comprising communicatively coupled computing devices. Furthermore, while the cloud network 102 is shown in FIG. 1B as having three of the computing devices 106, in some embodiments, the cloud network 102 comprises fewer (or more than) three computing devices 106.

The media playback system 100 is configured to receive media content from the networks 102 via the links 103. The received media content can comprise, for example, a Uniform Resource Identifier (URI) and/or a Uniform Resource Locator (URL). For instance, in some examples, the media playback system 100 can stream, download, or otherwise obtain data from a URI or a URL corresponding to the received media content. A network 104 communicatively couples the links 103 and at least a portion of the devices (e.g., one or more of the playback devices 110, NMDs 120, and/or control devices 130) of the media playback system 100. The network 104 can include, for example, a wireless network (e.g., a WiFi network, a Bluetooth, a Z-Wave network, a ZigBee, and/or other suitable wireless communication protocol network) and/or a wired network (e.g., a network comprising Ethernet, Universal Serial Bus (USB), and/or another suitable wired communication). As those of ordinary skill in the art will appreciate, as used herein, “WiFi” can refer to several different communication protocols including, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ac, 802.11ad, 802.11af, 802.11ah, 802.11ai, 802.11aj, 802.11aq, 802.11ax, 802.11ay, 802.15, etc. transmitted at 2.4 Gigahertz (GHz), 5 GHz, and/or another suitable frequency.

In some embodiments, the network 104 comprises a dedicated communication network that the media playback system 100 uses to transmit messages between individual devices and/or to transmit media content to and from media content sources (e.g., one or more of the computing devices 106). In certain embodiments, the network 104 is configured to be accessible only to devices in the media playback system 100, thereby reducing interference and competition with other household devices. In other embodiments, however, the network 104 comprises an existing household communication network (e.g., a household WiFi network). In some embodiments, the links 103 and the network 104 comprise one or more of the same networks. In some aspects, for example, the links 103 and the network 104 comprise a telecommunication network (e.g., an LTE network, a 5G network). Moreover, in some embodiments, the media playback system 100 is implemented without the network 104, and devices comprising the media playback system 100 can communicate with each other, for example, via one or more direct connections, PANs, telecommunication networks, and/or other suitable communication links. The network 104 may be referred to herein as a “local communication network” to differentiate the network 104 from the cloud network 102 that couples the media playback system 100 to remote devices, such as cloud services.

In some embodiments, audio content sources may be regularly added or removed from the media playback system 100. In some embodiments, for example, the media playback system 100 performs an indexing of media items when one or more media content sources are updated, added to, and/or removed from the media playback system 100. The media playback system 100 can scan identifiable media items in some or all folders and/or directories accessible to the playback devices 110, and generate or update a media content database comprising metadata (e.g., title, artist, album, track length) and other associated information (e.g., URIs, URLs) for each identifiable media item found. In some embodiments, for example, the media content database is stored on one or more of the playback devices 110, network microphone devices 120, and/or control devices 130.

In the illustrated embodiment of FIG. 1B, the playback devices 110 l and 110 m comprise a group 107 a. The playback devices 110 l and 110 m can be positioned in different rooms in a household and be grouped together in the group 107 a on a temporary or permanent basis based on user input received at the control device 130 a and/or another control device 130 in the media playback system 100. When arranged in the group 107 a, the playback devices 110 l and 110 m can be configured to play back the same or similar audio content in synchrony from one or more audio content sources. In certain embodiments, for example, the group 107 a comprises a bonded zone in which the playback devices 110 l and 110 m comprise left audio and right audio channels, respectively, of multi-channel audio content, thereby producing or enhancing a stereo effect of the audio content. In some embodiments, the group 107 a includes additional playback devices 110. In other embodiments, however, the media playback system 100 omits the group 107 a and/or other grouped arrangements of the playback devices 110. Additional details regarding groups and other arrangements of playback devices are described in further detail below with respect to FIGS. 1-I through IM.

The media playback system 100 includes the NMDs 120 a and 120 d, each comprising one or more microphones configured to receive voice utterances from a user. In the illustrated embodiment of FIG. 1B, the NMD 120 a is a standalone device and the NMD 120 d is integrated into the playback device 110 n. The NMD 120 a, for example, is configured to receive voice input 121 from a user 123. In some embodiments, the NMD 120 a transmits data associated with the received voice input 121 to a voice assistant service (VAS) configured to (i) process the received voice input data and (ii) facilitate one or more operations on behalf of the media playback system 100.

In some aspects, for example, the computing device 106 c comprises one or more modules and/or servers of a VAS (e.g., a VAS operated by one or more of SONOS®, AMAZON®, GOOGLE® APPLE®, MICROSOFT®). The computing device 106 c can receive the voice input data from the NMD 120 a via the network 104 and the links 103.

In response to receiving the voice input data, the computing device 106 c processes the voice input data (i.e., “Play Hey Jude by The Beatles”), and determines that the processed voice input includes a command to play a song (e.g., “Hey Jude”). In some embodiments, after processing the voice input, the computing device 106 c accordingly transmits commands to the media playback system 100 to play back “Hey Jude” by the Beatles from a suitable media service (e.g., via one or more of the computing devices 106) on one or more of the playback devices 110. In other embodiments, the computing device 106 c may be configured to interface with media services on behalf of the media playback system 100. In such embodiments, after processing the voice input, instead of the computing device 106 c transmitting commands to the media playback system 100 causing the media playback system 100 to retrieve the requested media from a suitable media service, the computing device 106 c itself causes a suitable media service to provide the requested media to the media playback system 100 in accordance with the user's voice utterance.

b. Suitable Playback Devices

FIG. 1C is a block diagram of the playback device 110 a comprising an input/output 111. The input/output 111 can include an analog I/O 111 a (e.g., one or more wires, cables, and/or other suitable communication links configured to carry analog signals) and/or a digital I/O 111 b (e.g., one or more wires, cables, or other suitable communication links configured to carry digital signals). In some embodiments, the analog I/O 111 a is an audio line-in input connection comprising, for example, an auto-detecting 3.5 mm audio line-in connection. In some embodiments, the digital I/O 111 b comprises a Sony/Philips Digital Interface Format (S/PDIF) communication interface and/or cable and/or a Toshiba Link (TOSLINK) cable. In some embodiments, the digital I/O 111 b comprises a High-Definition Multimedia Interface (HDMI) interface and/or cable. In some embodiments, the digital I/O 111 b includes one or more wireless communication links comprising, for example, a radio frequency (RF), infrared, WiFi, Bluetooth, or another suitable communication protocol. In certain embodiments, the analog I/O 111 a and the digital I/O 111 b comprise interfaces (e.g., ports, plugs, jacks) configured to receive connectors of cables transmitting analog and digital signals, respectively, without necessarily including cables.

The playback device 110 a, for example, can receive media content (e.g., audio content comprising music and/or other sounds) from a local audio source 105 via the input/output 111 (e.g., a cable, a wire, a PAN, a Bluetooth connection, an ad hoc wired or wireless communication network, and/or another suitable communication link). The local audio source 105 can comprise, for example, a mobile device (e.g., a smartphone, a tablet, a laptop computer) or another suitable audio component (e.g., a television, a desktop computer, an amplifier, a phonograph, a Blu-ray player, a memory storing digital media files). In some aspects, the local audio source 105 includes local music libraries on a smartphone, a computer, a networked-attached storage (NAS), and/or another suitable device configured to store media files. In certain embodiments, one or more of the playback devices 110, NMDs 120, and/or control devices 130 comprise the local audio source 105. In other embodiments, however, the media playback system omits the local audio source 105 altogether. In some embodiments, the playback device 110 a does not include an input/output 111 and receives all audio content via the network 104.

The playback device 110 a further comprises electronics 112, a user interface 113 (e.g., one or more buttons, knobs, dials, touch-sensitive surfaces, displays, touchscreens), and one or more transducers 114 (referred to hereinafter as “the transducers 114”). The electronics 112 are configured to receive audio from an audio source (e.g., the local audio source 105) via the input/output 111 or one or more of the computing devices 106 a-c via the network 104 (FIG. 1B)), amplify the received audio, and output the amplified audio for playback via one or more of the transducers 114. In some embodiments, the playback device 110 a optionally includes one or more microphones 115 (e.g., a single microphone, a plurality of microphones, a microphone array) (hereinafter referred to as “the microphones 115”). In certain embodiments, for example, the playback device 110 a having one or more of the optional microphones 115 can operate as an NMD configured to receive voice input from a user and correspondingly perform one or more operations based on the received voice input.

In the illustrated embodiment of FIG. 1C, the electronics 112 comprise one or more processors 112 a (referred to hereinafter as “the processors 112 a”), memory 112 b, software components 112 c, a network interface 112 d, one or more audio processing components 112 g (referred to hereinafter as “the audio components 112 g”), one or more audio amplifiers 112 h (referred to hereinafter as “the amplifiers 112 h”), and power 112 i (e.g., one or more power supplies, power cables, power receptacles, batteries, induction coils, Power-over Ethernet (POE) interfaces, and/or other suitable sources of electric power). In some embodiments, the electronics 112 optionally include one or more other components 112 j (e.g., one or more sensors, video displays, touchscreens, battery charging bases).

The processors 112 a can comprise clock-driven computing component(s) configured to process data, and the memory 112 b can comprise a computer-readable medium (e.g., a tangible, non-transitory computer-readable medium loaded with one or more of the software components 112 c) configured to store instructions for performing various operations and/or functions. The processors 112 a are configured to execute the instructions stored on the memory 112 b to perform one or more of the operations. The operations can include, for example, causing the playback device 110 a to retrieve audio data from an audio source (e.g., one or more of the computing devices 106 a-c (FIG. 1B)), and/or another one of the playback devices 110. In some embodiments, the operations further include causing the playback device 110 a to send audio data to another one of the playback devices 110 a and/or another device (e.g., one of the NMDs 120). Certain embodiments include operations causing the playback device 110 a to pair with another of the one or more playback devices 110 to enable a multi-channel audio environment (e.g., a stereo pair, a bonded zone).

The processors 112 a can be further configured to perform operations causing the playback device 110 a to synchronize playback of audio content with another of the one or more playback devices 110. As those of ordinary skill in the art will appreciate, during synchronous playback of audio content on a plurality of playback devices, a listener will preferably be unable to perceive time-delay differences between playback of the audio content by the playback device 110 a and the other one or more other playback devices 110. Additional details regarding audio playback synchronization among playback devices can be found, for example, in U.S. Pat. No. 8,234,395, which was incorporated by reference above.

In some embodiments, the memory 112 b is further configured to store data associated with the playback device 110 a, such as one or more zones and/or zone groups of which the playback device 110 a is a member, audio sources accessible to the playback device 110 a, and/or a playback queue that the playback device 110 a (and/or another of the one or more playback devices) can be associated with. The stored data can comprise one or more state variables that are periodically updated and used to describe a state of the playback device 110 a. The memory 112 b can also include data associated with a state of one or more of the other devices (e.g., the playback devices 110, NMDs 120, control devices 130) of the media playback system 100. In some aspects, for example, the state data is shared during predetermined intervals of time (e.g., every 5 seconds, every 10 seconds, every 60 seconds) among at least a portion of the devices of the media playback system 100, so that one or more of the devices have the most recent data associated with the media playback system 100.

The network interface 112 d is configured to facilitate a transmission of data between the playback device 110 a and one or more other devices on a data network such as, for example, the links 103 and/or the network 104 (FIG. 1B). The network interface 112 d is configured to transmit and receive data corresponding to media content (e.g., audio content, video content, text, photographs) and other signals (e.g., non-transitory signals) comprising digital packet data including an Internet Protocol (IP)-based source address and/or an IP-based destination address. The network interface 112 d can parse the digital packet data such that the electronics 112 properly receives and processes the data destined for the playback device 110 a.

In the illustrated embodiment of FIG. 1C, the network interface 112 d comprises one or more wireless interfaces 112 e (referred to hereinafter as “the wireless interface 112 e”). The wireless interface 112 e (e.g., a suitable interface comprising one or more antennae) can be configured to wirelessly communicate with one or more other devices (e.g., one or more of the other playback devices 110, NMDs 120, and/or control devices 130) that are communicatively coupled to the network 104 (FIG. 1B) in accordance with a suitable wireless communication protocol (e.g., WiFi, Bluetooth, LTE). In some embodiments, the network interface 112 d optionally includes a wired interface 112 f (e.g., an interface or receptacle configured to receive a network cable such as an Ethernet, a USB-A, USB-C, and/or Thunderbolt cable) configured to communicate over a wired connection with other devices in accordance with a suitable wired communication protocol. In certain embodiments, the network interface 112 d includes the wired interface 112 f and excludes the wireless interface 112 e. In some embodiments, the electronics 112 excludes the network interface 112 d altogether and transmits and receives media content and/or other data via another communication path (e.g., the input/output 111).

The audio components 112 g are configured to process and/or filter data comprising media content received by the electronics 112 (e.g., via the input/output 111 and/or the network interface 112 d) to produce output audio signals. In some embodiments, the audio processing components 112 g comprise, for example, one or more digital-to-analog converters (DAC), audio preprocessing components, audio enhancement components, a digital signal processors (DSPs), and/or other suitable audio processing components, modules, circuits, etc. In certain embodiments, one or more of the audio processing components 112 g can comprise one or more subcomponents of the processors 112 a. In some embodiments, the electronics 112 omits the audio processing components 112 g. In some aspects, for example, the processors 112 a execute instructions stored on the memory 112 b to perform audio processing operations to produce the output audio signals.

The amplifiers 112 h are configured to receive and amplify the audio output signals produced by the audio processing components 112 g and/or the processors 112 a. The amplifiers 112 h can comprise electronic devices and/or components configured to amplify audio signals to levels sufficient for driving one or more of the transducers 114. In some embodiments, for example, the amplifiers 112 h include one or more switching or class-D power amplifiers. In other embodiments, however, the amplifiers include one or more other types of power amplifiers (e.g., linear gain power amplifiers, class-A amplifiers, class-B amplifiers, class-AB amplifiers, class-C amplifiers, class-D amplifiers, class-E amplifiers, class-F amplifiers, class-G and/or class H amplifiers, and/or another suitable type of power amplifier). In certain embodiments, the amplifiers 112 h comprise a suitable combination of two or more of the foregoing types of power amplifiers. Moreover, in some embodiments, individual ones of the amplifiers 112 h correspond to individual ones of the transducers 114. In other embodiments, however, the electronics 112 includes a single one of the amplifiers 112 h configured to output amplified audio signals to a plurality of the transducers 114. In some other embodiments, the electronics 112 omits the amplifiers 112 h.

The transducers 114 (e.g., one or more speakers and/or speaker drivers) receive the amplified audio signals from the amplifier 112 h and render or output the amplified audio signals as sound (e.g., audible sound waves having a frequency between about 20 Hertz (Hz) and 20 kilohertz (kHz)). In some embodiments, the transducers 114 can comprise a single transducer. In other embodiments, however, the transducers 114 comprise a plurality of audio transducers. In some embodiments, the transducers 114 comprise more than one type of transducer. For example, the transducers 114 can include one or more low frequency transducers (e.g., subwoofers, woofers), mid-range frequency transducers (e.g., mid-range transducers, mid-woofers), and one or more high frequency transducers (e.g., one or more tweeters). As used herein, “low frequency” can generally refer to audible frequencies below about 500 Hz, “mid-range frequency” can generally refer to audible frequencies between about 500 Hz and about 2 kHz, and “high frequency” can generally refer to audible frequencies above 2 kHz. In certain embodiments, however, one or more of the transducers 114 comprise transducers that do not adhere to the foregoing frequency ranges. For example, one of the transducers 114 may comprise a mid-woofer transducer configured to output sound at frequencies between about 200 Hz and about 5 kHz.

By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including, for example, a “SONOS ONE,” “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “PLAYBASE,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Other suitable playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, one of ordinary skilled in the art will appreciate that a playback device is not limited to the examples described herein or to SONOS product offerings. In some embodiments, for example, one or more playback devices 110 comprises wired or wireless headphones (e.g., over-the-ear headphones, on-ear headphones, in-ear earphones). In other embodiments, one or more of the playback devices 110 comprise a docking station and/or an interface configured to interact with a docking station for personal mobile media playback devices. In certain embodiments, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use. In some embodiments, a playback device omits a user interface and/or one or more transducers. For example, FIG. 1D is a block diagram of a playback device 110 p comprising the input/output 111 and electronics 112 without the user interface 113 or transducers 114.

FIG. 1E is a block diagram of a bonded playback device 110 q comprising the playback device 110 a (FIG. 1C) sonically bonded with the playback device 110 i (e.g., a subwoofer) (FIG. 1A). In the illustrated embodiment, the playback devices 110 a and 110 i are separate ones of the playback devices 110 housed in separate enclosures. In some embodiments, however, the bonded playback device 110 q comprises a single enclosure housing both the playback devices 110 a and 110 i. The bonded playback device 110 q can be configured to process and reproduce sound differently than an unbonded playback device (e.g., the playback device 110 a of FIG. 1C) and/or paired or bonded playback devices (e.g., the playback devices 110 l and 110 m of FIG. 1B). In some embodiments, for example, the playback device 110 a is full-range playback device configured to render low frequency, mid-range frequency, and high frequency audio content, and the playback device 110 i is a subwoofer configured to render low frequency audio content. In some aspects, the playback device 110 a, when bonded with the first playback device, is configured to render only the mid-range and high frequency components of a particular audio content, while the playback device 110 i renders the low frequency component of the particular audio content. In some embodiments, the bonded playback device 110 q includes additional playback devices and/or another bonded playback device. Additional playback device embodiments are described in further detail below with respect to FIGS. 2A-3D.

c. Suitable Network Microphone Devices (NMDs)

FIG. 1F is a block diagram of the NMD 120 a (FIGS. 1A and 1B). The NMD 120 a includes one or more voice processing components 124 (hereinafter “the voice components 124”) and several components described with respect to the playback device 110 a (FIG. 1C) including the processors 112 a, the memory 112 b, and the microphones 115. The NMD 120 a optionally comprises other components also included in the playback device 110 a (FIG. 1C), such as the user interface 113 and/or the transducers 114. In some embodiments, the NMD 120 a is configured as a media playback device (e.g., one or more of the playback devices 110), and further includes, for example, one or more of the audio components 112 g (FIG. 1C), the amplifiers 114, and/or other playback device components. In certain embodiments, the NMD 120 a comprises an Internet of Things (IoT) device such as, for example, a thermostat, alarm panel, fire and/or smoke detector, etc. In some embodiments, the NMD 120 a comprises the microphones 115, the voice processing 124, and only a portion of the components of the electronics 112 described above with respect to FIG. 1B. In some aspects, for example, the NMD 120 a includes the processor 112 a and the memory 112 b (FIG. 1B), while omitting one or more other components of the electronics 112. In some embodiments, the NMD 120 a includes additional components (e.g., one or more sensors, cameras, thermometers, barometers, hygrometers).

In some embodiments, an NMD can be integrated into a playback device. FIG. 1G is a block diagram of a playback device 110 r comprising an NMD 120 d. The playback device 110 r can comprise many or all of the components of the playback device 110 a and further include the microphones 115 and voice processing 124 (FIG. 1F). The playback device 110 r optionally includes an integrated control device 130 c. The control device 130 c can comprise, for example, a user interface (e.g., the user interface 113 of FIG. 1B) configured to receive user input (e.g., touch input, voice input) without a separate control device. In other embodiments, however, the playback device 110 r receives commands from another control device (e.g., the control device 130 a of FIG. 1B). Additional NMD embodiments are described in further detail below with respect to FIGS. 3A-3F.

Referring again to FIG. 1F, the microphones 115 are configured to acquire, capture, and/or receive sound from an environment (e.g., the environment 101 of FIG. 1A) and/or a room in which the NMD 120 a is positioned. The received sound can include, for example, vocal utterances, audio played back by the NMD 120 a and/or another playback device, background voices, ambient sounds, etc. The microphones 115 convert the received sound into electrical signals to produce microphone data. The voice processing 124 receives and analyzes the microphone data to determine whether a voice input is present in the microphone data. The voice input can comprise, for example, an activation word followed by an utterance including a user request. As those of ordinary skill in the art will appreciate, an activation word is a word or other audio cue signifying a user voice input. For instance, in querying the AMAZON® VAS, a user might speak the activation word “Alexa.” Other examples include “Ok, Google” for invoking the GOOGLE® VAS and “Hey, Siri” for invoking the APPLE® VAS.

After detecting the activation word, voice processing 124 monitors the microphone data for an accompanying user request in the voice input. The user request may include, for example, a command to control a third-party device, such as a thermostat (e.g., NEST® thermostat), an illumination device (e.g., a PHILIPS HUE® lighting device), or a media playback device (e.g., a Sonos® playback device). For example, a user might speak the activation word “Alexa” followed by the utterance “set the thermostat to 68 degrees” to set a temperature in a home (e.g., the environment 101 of FIG. 1A). The user might speak the same activation word followed by the utterance “turn on the living room” to turn on illumination devices in a living room area of the home. The user may similarly speak an activation word followed by a request to play a particular song, an album, or a playlist of music on a playback device in the home. Additional description regarding receiving and processing voice input data can be found in further detail below with respect to FIGS. 3A-3F.

d. Suitable Control Devices

FIG. 1H is a partial schematic diagram of the control device 130 a (FIGS. 1A and 1B). As used herein, the term “control device” can be used interchangeably with “controller” or “control system.” Among other features, the control device 130 a is configured to receive user input related to the media playback system 100 and, in response, cause one or more devices in the media playback system 100 to perform an action(s) or operation(s) corresponding to the user input. In the illustrated embodiment, the control device 130 a comprises a smartphone (e.g., an iPhone™, an Android phone) on which media playback system controller application software is installed. In some embodiments, the control device 130 a comprises, for example, a tablet (e.g., an iPad™), a computer (e.g., a laptop computer, a desktop computer), and/or another suitable device (e.g., a television, an automobile audio head unit, an IoT device). In certain embodiments, the control device 130 a comprises a dedicated controller for the media playback system 100. In other embodiments, as described above with respect to FIG. 1G, the control device 130 a is integrated into another device in the media playback system 100 (e.g., one more of the playback devices 110, NMDs 120, and/or other suitable devices configured to communicate over a network).

The control device 130 a includes electronics 132, a user interface 133, one or more speakers 134, and one or more microphones 135. The electronics 132 comprise one or more processors 132 a (referred to hereinafter as “the processors 132 a”), a memory 132 b, software components 132 c, and a network interface 132 d. The processor 132 a can be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 100. The memory 132 b can comprise data storage that can be loaded with one or more of the software components executable by the processor 302 to perform those functions. The software components 132 c can comprise applications and/or other executable software configured to facilitate control of the media playback system 100. The memory 112 b can be configured to store, for example, the software components 132 c, media playback system controller application software, and/or other data associated with the media playback system 100 and the user.

The network interface 132 d is configured to facilitate network communications between the control device 130 a and one or more other devices in the media playback system 100, and/or one or more remote devices. In some embodiments, the network interface 132 d is configured to operate according to one or more suitable communication industry standards (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G, LTE). The network interface 132 d can be configured, for example, to transmit data to and/or receive data from the playback devices 110, the NMDs 120, other ones of the control devices 130, one of the computing devices 106 of FIG. 1B, devices comprising one or more other media playback systems, etc. The transmitted and/or received data can include, for example, playback device control commands, state variables, playback zone and/or zone group configurations. For instance, based on user input received at the user interface 133, the network interface 132 d can transmit a playback device control command (e.g., volume control, audio playback control, audio content selection) from the control device 304 to one or more of the playback devices 100. The network interface 132 d can also transmit and/or receive configuration changes such as, for example, adding/removing one or more playback devices 100 to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Additional description of zones and groups can be found below with respect to FIGS. 1-I through 1M.

The user interface 133 is configured to receive user input and can facilitate control of the media playback system 100. The user interface 133 includes media content art 133 a (e.g., album art, lyrics, videos), a playback status indicator 133 b (e.g., an elapsed and/or remaining time indicator), media content information region 133 c, a playback control region 133 d, and a zone indicator 133 e. The media content information region 133 c can include a display of relevant information (e.g., title, artist, album, genre, release year) about media content currently playing and/or media content in a queue or playlist. The playback control region 133 d can include selectable (e.g., via touch input and/or via a cursor or another suitable selector) icons to cause one or more playback devices in a selected playback zone or zone group to perform playback actions such as, for example, play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode, etc. The playback control region 133 d may also include selectable icons to modify equalization settings, playback volume, and/or other suitable playback actions. In the illustrated embodiment, the user interface 133 comprises a display presented on a touch screen interface of a smartphone (e.g., an iPhone™, an Android phone). In some embodiments, however, user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

The one or more speakers 134 (e.g., one or more transducers) can be configured to output sound to the user of the control device 130 a. In some embodiments, the one or more speakers comprise individual transducers configured to correspondingly output low frequencies, mid-range frequencies, and/or high frequencies. In some aspects, for example, the control device 130 a is configured as a playback device (e.g., one of the playback devices 110). Similarly, in some embodiments the control device 130 a is configured as an NMD (e.g., one of the NMDs 120), receiving voice commands and other sounds via the one or more microphones 135.

The one or more microphones 135 can comprise, for example, one or more condenser microphones, electret condenser microphones, dynamic microphones, and/or other suitable types of microphones or transducers. In some embodiments, two or more of the microphones 135 are arranged to capture location information of an audio source (e.g., voice, audible sound) and/or configured to facilitate filtering of background noise. Moreover, in certain embodiments, the control device 130 a is configured to operate as playback device and an NMD. In other embodiments, however, the control device 130 a omits the one or more speakers 134 and/or the one or more microphones 135. For instance, the control device 130 a may comprise a device (e.g., a thermostat, an IoT device, a network device) comprising a portion of the electronics 132 and the user interface 133 (e.g., a touch screen) without any speakers or microphones. Additional control device embodiments are described in further detail below with respect to FIGS. 4A-4D and 5.

e. Suitable Playback Device Configurations

FIGS. 1-1 through 1M show example configurations of playback devices in zones and zone groups. Referring first to FIG. 1M, in one example, a single playback device may belong to a zone. For example, the playback device 110 g in the second bedroom 101 c (FIG. 1A) may belong to Zone C. In some implementations described below, multiple playback devices may be “bonded” to form a “bonded pair” which together form a single zone. For example, the playback device 110 l (e.g., a left playback device) can be bonded to the playback device 110 l (e.g., a left playback device) to form Zone A. Bonded playback devices may have different playback responsibilities (e.g., channel responsibilities). In another implementation described below, multiple playback devices may be merged to form a single zone. For example, the playback device 110 h (e.g., a front playback device) may be merged with the playback device 110 i (e.g., a subwoofer), and the playback devices 110 j and 110 k (e.g., left and right surround speakers, respectively) to form a single Zone D. In another example, the playback devices 110 g and 110 h can be merged to form a merged group or a zone group 108 b. The merged playback devices 110 g and 110 h may not be specifically assigned different playback responsibilities. That is, the merged playback devices 110 h and 110 i may, aside from playing audio content in synchrony, each play audio content as they would if they were not merged.

Each zone in the media playback system 100 may be provided for control as a single user interface (UI) entity. For example, Zone A may be provided as a single entity named Master Bathroom. Zone B may be provided as a single entity named Master Bedroom. Zone C may be provided as a single entity named Second Bedroom.

Playback devices that are bonded may have different playback responsibilities, such as responsibilities for certain audio channels. For example, as shown in FIG. 1-I, the playback devices 110 l and 110 m may be bonded so as to produce or enhance a stereo effect of audio content. In this example, the playback device 110 l may be configured to play a left channel audio component, while the playback device 110 k may be configured to play a right channel audio component. In some implementations, such stereo bonding may be referred to as “pairing.”

Additionally, bonded playback devices may have additional and/or different respective speaker drivers. As shown in FIG. 1J, the playback device 110 h named Front may be bonded with the playback device 110 i named SUB. The Front device 110 h can be configured to render a range of mid to high frequencies and the SUB device 110 i can be configured render low frequencies. When unbonded, however, the Front device 110 h can be configured render a full range of frequencies. As another example, FIG. 1K shows the Front and SUB devices 110 h and 110 i further bonded with Left and Right playback devices 110 j and 110 k, respectively. In some implementations, the Right and Left devices 110 j and 102 k can be configured to form surround or “satellite” channels of a home theater system. The bonded playback devices 110 h, 110 i, 110 j, and 110 k may form a single Zone D (FIG. 1M).

Playback devices that are merged may not have assigned playback responsibilities, and may each render the full range of audio content the respective playback device is capable of. Nevertheless, merged devices may be represented as a single UI entity (i.e., a zone, as discussed above). For instance, the playback devices 110 a and 110 n the master bathroom have the single UI entity of Zone A. In one embodiment, the playback devices 110 a and 110 n may each output the full range of audio content each respective playback devices 110 a and 110 n are capable of, in synchrony.

In some embodiments, an NMD is bonded or merged with another device so as to form a zone. For example, the NMD 120 b may be bonded with the playback device 110 e, which together form Zone F, named Living Room. In other embodiments, a stand-alone network microphone device may be in a zone by itself. In other embodiments, however, a stand-alone network microphone device may not be associated with a zone. Additional details regarding associating network microphone devices and playback devices as designated or default devices may be found, for example, in U.S. Patent Publication No. 2017/0242653 titled “Voice Control of a Media Playback System,” the disclosure of which is hereby incorporated by reference herein in its entirety.

Zones of individual, bonded, and/or merged devices may be grouped to form a zone group. For example, referring to FIG. 1M, Zone A may be grouped with Zone B to form a zone group 108 a that includes the two zones. Similarly, Zone G may be grouped with Zone H to form the zone group 108 b. As another example, Zone A may be grouped with one or more other Zones C-I. The Zones A-I may be grouped and ungrouped in numerous ways. For example, three, four, five, or more (e.g., all) of the Zones A-I may be grouped. When grouped, the zones of individual and/or bonded playback devices may play back audio in synchrony with one another, as described in previously referenced U.S. Pat. No. 8,234,395. Playback devices may be dynamically grouped and ungrouped to form new or different groups that synchronously play back audio content.

In various implementations, the zones in an environment may be the default name of a zone within the group or a combination of the names of the zones within a zone group. For example, Zone Group 108 b can have be assigned a name such as “Dining+Kitchen”, as shown in FIG. 1M. In some embodiments, a zone group may be given a unique name selected by a user.

Certain data may be stored in a memory of a playback device (e.g., the memory 112 c of FIG. 1C) as one or more state variables that are periodically updated and used to describe the state of a playback zone, the playback device(s), and/or a zone group associated therewith. The memory may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system.

In some embodiments, the memory may store instances of various variable types associated with the states. Variables instances may be stored with identifiers (e.g., tags) corresponding to type. For example, certain identifiers may be a first type “a1” to identify playback device(s) of a zone, a second type “b1” to identify playback device(s) that may be bonded in the zone, and a third type “c1” to identify a zone group to which the zone may belong. As a related example, identifiers associated with the second bedroom 101 c may indicate that the playback device is the only playback device of the Zone C and not in a zone group. Identifiers associated with the Den may indicate that the Den is not grouped with other zones but includes bonded playback devices 110 h-110 k. Identifiers associated with the Dining Room may indicate that the Dining Room is part of the Dining+Kitchen zone group 108 b and that devices 110 b and 110 d are grouped (FIG. 1L). Identifiers associated with the Kitchen may indicate the same or similar information by virtue of the Kitchen being part of the Dining+Kitchen zone group 108 b. Other example zone variables and identifiers are described below.

In yet another example, the media playback system 100 may store variables or identifiers representing other associations of zones and zone groups, such as identifiers associated with Areas, as shown in FIG. 1M. An area may involve a cluster of zone groups and/or zones not within a zone group. For instance, FIG. 1M shows an Upper Area 109 a including Zones A-D, and a Lower Area 109 b including Zones E-I. In one aspect, an Area may be used to invoke a cluster of zone groups and/or zones that share one or more zones and/or zone groups of another cluster. In another aspect, this differs from a zone group, which does not share a zone with another zone group. Further examples of techniques for implementing Areas may be found, for example, in U.S. Patent Publication No. 2018/0107446 filed Aug. 21, 2017 and titled “Room Association Based on Name,” and U.S. Pat. No. 8,483,853 filed Sep. 11, 2007, and titled “Controlling and manipulating groupings in a multi-zone media system.” One playback device in a group can be identified as a group coordinator for the group, such as described in U.S. Patent Publication No. 2017/0192739 titled “Group Coordinator Selection.” Each of these applications is incorporated herein by reference in its entirety. In some embodiments, the media playback system 100 may not implement Areas, in which case the system may not store variables associated with Areas.

III. Example Systems and Devices

FIG. 2A is a front isometric view of a playback device 210 configured in accordance with aspects of the disclosed technology. FIG. 2B is a front isometric view of the playback device 210 without a grille 216 e. FIG. 2C is an exploded view of the playback device 210. Referring to FIGS. 2A-2C together, the playback device 210 comprises a housing 216 that includes an upper portion 216 a, a right or first side portion 216 b, a lower portion 216 c, a left or second side portion 216 d, the grille 216 e, and a rear portion 216 f. A plurality of fasteners 216 g (e.g., one or more screws, rivets, clips) attaches a frame 216 h to the housing 216. A cavity 216 j (FIG. 2C) in the housing 216 is configured to receive the frame 216 h and electronics 212. The frame 216 h is configured to carry a plurality of transducers 214 (identified individually in FIG. 2B as transducers 214 a-f). The electronics 212 (e.g., the electronics 112 of FIG. 1C) is configured to receive audio content from an audio source and send electrical signals corresponding to the audio content to the transducers 214 for playback.

The transducers 214 are configured to receive the electrical signals from the electronics 112, and further configured to convert the received electrical signals into audible sound during playback. For instance, the transducers 214 a-c (e.g., tweeters) can be configured to output high frequency sound (e.g., sound waves having a frequency greater than about 2 kHz). The transducers 214 d-f (e.g., mid-woofers, woofers, midrange speakers) can be configured output sound at frequencies lower than the transducers 214 a-c (e.g., sound waves having a frequency lower than about 2 kHz). In some embodiments, the playback device 210 includes a number of transducers different than those illustrated in FIGS. 2A-2C. For example, as described in further detail below with respect to FIGS. 3A-3C, the playback device 210 can include fewer than six transducers (e.g., one, two, three). In other embodiments, however, the playback device 210 includes more than six transducers (e.g., nine, ten). Moreover, in some embodiments, all or a portion of the transducers 214 are configured to operate as a phased array to desirably adjust (e.g., narrow or widen) a radiation pattern of the transducers 214, thereby altering a user's perception of the sound emitted from the playback device 210.

In the illustrated embodiment of FIGS. 2A-2C, a filter 216 i is axially aligned with the transducer 214 b. The filter 216 i can be configured to desirably attenuate a predetermined range of frequencies that the transducer 214 b outputs to improve sound quality and a perceived sound stage output collectively by the transducers 214. In some embodiments, however, the playback device 210 omits the filter 216 i. In other embodiments, the playback device 210 includes one or more additional filters aligned with the transducers 214 b and/or at least another of the transducers 214.

FIGS. 3A and 3B are front and right isometric side views, respectively, of an NMD 320 configured in accordance with embodiments of the disclosed technology. FIG. 3C is an exploded view of the NMD 320. FIG. 3D is an enlarged view of a portion of FIG. 3B including a user interface 313 of the NMD 320. Referring first to FIGS. 3A-3C, the NMD 320 includes a housing 316 comprising an upper portion 316 a, a lower portion 316 b and an intermediate portion 316 c (e.g., a grille). A plurality of ports, holes or apertures 316 d in the upper portion 316 a allow sound to pass through to one or more microphones 315 (FIG. 3C) positioned within the housing 316. The one or more microphones 316 are configured to received sound via the apertures 316 d and produce electrical signals based on the received sound. In the illustrated embodiment, a frame 316 e (FIG. 3C) of the housing 316 surrounds cavities 316 f and 316 g configured to house, respectively, a first transducer 314 a (e.g., a tweeter) and a second transducer 314 b (e.g., a mid-woofer, a midrange speaker, a woofer). In other embodiments, however, the NMD 320 includes a single transducer, or more than two (e.g., two, five, six) transducers. In certain embodiments, the NMD 320 omits the transducers 314 a and 314 b altogether.

Electronics 312 (FIG. 3C) includes components configured to drive the transducers 314 a and 314 b, and further configured to analyze audio data corresponding to the electrical signals produced by the one or more microphones 315. In some embodiments, for example, the electronics 312 comprises many or all of the components of the electronics 112 described above with respect to FIG. 1C. In certain embodiments, the electronics 312 includes components described above with respect to FIG. 1F such as, for example, the one or more processors 112 a, the memory 112 b, the software components 112 c, the network interface 112 d, etc. In some embodiments, the electronics 312 includes additional suitable components (e.g., proximity or other sensors).

Referring to FIG. 3D, the user interface 313 includes a plurality of control surfaces (e.g., buttons, knobs, capacitive surfaces) including a first control surface 313 a (e.g., a previous control), a second control surface 313 b (e.g., a next control), and a third control surface 313 c (e.g., a play and/or pause control). A fourth control surface 313 d is configured to receive touch input corresponding to activation and deactivation of the one or microphones 315. A first indicator 313 e (e.g., one or more light emitting diodes (LEDs) or another suitable illuminator) can be configured to illuminate only when the one or more microphones 315 are activated. A second indicator 313 f (e.g., one or more LEDs) can be configured to remain solid during normal operation and to blink or otherwise change from solid to indicate a detection of voice activity. In some embodiments, the user interface 313 includes additional or fewer control surfaces and illuminators. In one embodiment, for example, the user interface 313 includes the first indicator 313 e, omitting the second indicator 313 f. Moreover, in certain embodiments, the NMD 320 comprises a playback device and a control device, and the user interface 313 comprises the user interface of the control device.

Referring to FIGS. 3A-3D together, the NMD 320 is configured to receive voice commands from one or more adjacent users via the one or more microphones 315. As described above with respect to FIG. 1B, the one or more microphones 315 can acquire, capture, or record sound in a vicinity (e.g., a region within 10 m or less of the NMD 320) and transmit electrical signals corresponding to the recorded sound to the electronics 312. The electronics 312 can process the electrical signals and can analyze the resulting audio data to determine a presence of one or more voice commands (e.g., one or more activation words). In some embodiments, for example, after detection of one or more suitable voice commands, the NMD 320 is configured to transmit a portion of the recorded audio data to another device and/or a remote server (e.g., one or more of the computing devices 106 of FIG. 1B) for further analysis. The remote server can analyze the audio data, determine an appropriate action based on the voice command, and transmit a message to the NMD 320 to perform the appropriate action. For instance, a user may speak “Sonos, play Michael Jackson.” The NMD 320 can, via the one or more microphones 315, record the user's voice utterance, determine the presence of a voice command, and transmit the audio data having the voice command to a remote server (e.g., one or more of the remote computing devices 106 of FIG. 1B, one or more servers of a VAS and/or another suitable service). The remote server can analyze the audio data and determine an action corresponding to the command. The remote server can then transmit a command to the NMD 320 to perform the determined action (e.g., play back audio content related to Michael Jackson). The NMD 320 can receive the command and play back the audio content related to Michael Jackson from a media content source. As described above with respect to FIG. 1B, suitable content sources can include a device or storage communicatively coupled to the NMD 320 via a LAN (e.g., the network 104 of FIG. 1B), a remote server (e.g., one or more of the remote computing devices 106 of FIG. 1B), etc. In certain embodiments, however, the NMD 320 determines and/or performs one or more actions corresponding to the one or more voice commands without intervention or involvement of an external device, computer, or server.

FIG. 3E is a functional block diagram showing additional features of the NMD 320 in accordance with aspects of the disclosure. The NMD 320 includes components configured to facilitate voice command capture including voice activity detector component(s) 312 k, beam former components 312 l, acoustic echo cancellation (AEC) and/or self-sound suppression components 312 m, activation word detector components 312 n, and voice/speech conversion components 312 o (e.g., voice-to-text and text-to-voice). In the illustrated embodiment of FIG. 3E, the foregoing components 312 k-312 o are shown as separate components. In some embodiments, however, one or more of the components 312 k-312 o are subcomponents of the processors 112 a.

The beamforming and self-sound suppression components 312 l and 312 m are configured to detect an audio signal and determine aspects of voice input represented in the detected audio signal, such as the direction, amplitude, frequency spectrum, etc. The voice activity detector activity components 312 k are operably coupled with the beamforming and AEC components 312 l and 312 m and are configured to determine a direction and/or directions from which voice activity is likely to have occurred in the detected audio signal. Potential speech directions can be identified by monitoring metrics which distinguish speech from other sounds. Such metrics can include, for example, energy within the speech band relative to background noise and entropy within the speech band, which is measure of spectral structure. As those of ordinary skill in the art will appreciate, speech typically has a lower entropy than most common background noise.

The activation word detector components 312 n are configured to monitor and analyze received audio to determine if any activation words (e.g., wake words) are present in the received audio. The activation word detector components 312 n may analyze the received audio using an activation word detection algorithm. If the activation word detector 312 n detects an activation word, the NMD 320 may process voice input contained in the received audio. Example activation word detection algorithms accept audio as input and provide an indication of whether an activation word is present in the audio. Many first- and third-party activation word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain activation words. In some embodiments, the activation word detector 312 n runs multiple activation word detection algorithms on the received audio simultaneously (or substantially simultaneously). As noted above, different voice services (e.g. AMAZON's ALEXA®, APPLE's SIRI®, or MICROSOFT's CORTANA®) can each use a different activation word for invoking their respective voice service. To support multiple services, the activation word detector 312 n may run the received audio through the activation word detection algorithm for each supported voice service in parallel.

The speech/text conversion components 312 o may facilitate processing by converting speech in the voice input to text. In some embodiments, the electronics 312 can include voice recognition software that is trained to a particular user or a particular set of users associated with a household. Such voice recognition software may implement voice-processing algorithms that are tuned to specific voice profile(s). Tuning to specific voice profiles may require less computationally intensive algorithms than traditional voice activity services, which typically sample from a broad base of users and diverse requests that are not targeted to media playback systems.

FIG. 3F is a schematic diagram of an example voice input 328 captured by the NMD 320 in accordance with aspects of the disclosure. The voice input 328 can include an activation word portion 328 a and a voice utterance portion 328 b. In some embodiments, the activation word 557 a can be a known activation word, such as “Alexa,” which is associated with AMAZON's ALEXA®. In other embodiments, however, the voice input 328 may not include an activation word. In some embodiments, a network microphone device may output an audible and/or visible response upon detection of the activation word portion 328 a. In addition or alternately, an NMB may output an audible and/or visible response after processing a voice input and/or a series of voice inputs.

The voice utterance portion 328 b may include, for example, one or more spoken commands (identified individually as a first command 328 c and a second command 328 e) and one or more spoken keywords (identified individually as a first keyword 328 d and a second keyword 328 f). In one example, the first command 328 c can be a command to play music, such as a specific song, album, playlist, etc. In this example, the keywords may be one or words identifying one or more zones in which the music is to be played, such as the Living Room and the Dining Room shown in FIG. 1A. In some examples, the voice utterance portion 328 b can include other information, such as detected pauses (e.g., periods of non-speech) between words spoken by a user, as shown in FIG. 3F. The pauses may demarcate the locations of separate commands, keywords, or other information spoke by the user within the voice utterance portion 328 b.

In some embodiments, the media playback system 100 is configured to temporarily reduce the volume of audio content that it is playing while detecting the activation word portion 557 a. The media playback system 100 may restore the volume after processing the voice input 328, as shown in FIG. 3F. Such a process can be referred to as ducking, examples of which are disclosed in U.S. Patent Publication No. 2017/0242653 titled “Voice Control of a Media Playback System,” the disclosure of which is hereby incorporated by reference herein in its entirety.

FIGS. 4A-4D are schematic diagrams of a control device 430 (e.g., the control device 130 a of FIG. 1H, a smartphone, a tablet, a dedicated control device, an IoT device, and/or another suitable device) showing corresponding user interface displays in various states of operation. A first user interface display 431 a (FIG. 4A) includes a display name 433 a (i.e., “Rooms”). A selected group region 433 b displays audio content information (e.g., artist name, track name, album art) of audio content played back in the selected group and/or zone. Group regions 433 c and 433 d display corresponding group and/or zone name, and audio content information audio content played back or next in a playback queue of the respective group or zone. An audio content region 433 e includes information related to audio content in the selected group and/or zone (i.e., the group and/or zone indicated in the selected group region 433 b). A lower display region 433 f is configured to receive touch input to display one or more other user interface displays. For example, if a user selects “Browse” in the lower display region 433 f, the control device 430 can be configured to output a second user interface display 431 b (FIG. 4B) comprising a plurality of music services 433 g (e.g., Spotify, Radio by Tunein, Apple Music, Pandora, Amazon, TV, local music, line-in) through which the user can browse and from which the user can select media content for play back via one or more playback devices (e.g., one of the playback devices 110 of FIG. 1A). Alternatively, if the user selects “My Sonos” in the lower display region 433 f, the control device 430 can be configured to output a third user interface display 431 c (FIG. 4C). A first media content region 433 h can include graphical representations (e.g., album art) corresponding to individual albums, stations, or playlists. A second media content region 433 i can include graphical representations (e.g., album art) corresponding to individual songs, tracks, or other media content. If the user selections a graphical representation 433 j (FIG. 4C), the control device 430 can be configured to begin play back of audio content corresponding to the graphical representation 433 j and output a fourth user interface display 431 d fourth user interface display 431 d includes an enlarged version of the graphical representation 433 j, media content information 433 k (e.g., track name, artist, album), transport controls 433 m (e.g., play, previous, next, pause, volume), and indication 433 n of the currently selected group and/or zone name.

FIG. 5 is a schematic diagram of a control device 530 (e.g., a laptop computer, a desktop computer). The control device 530 includes transducers 534, a microphone 535, and a camera 536. A user interface 531 includes a transport control region 533 a, a playback status region 533 b, a playback zone region 533 c, a playback queue region 533 d, and a media content source region 533 e. The transport control region comprises one or more controls for controlling media playback including, for example, volume, previous, play/pause, next, repeat, shuffle, track position, crossfade, equalization, etc. The audio content source region 533 e includes a listing of one or more media content sources from which a user can select media items for play back and/or adding to a playback queue.

The playback zone region 533 b can include representations of playback zones within the media playback system 100 (FIGS. 1A and 1B). In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, renaming of zone groups, etc. In the illustrated embodiment, a “group” icon is provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone can be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In the illustrated embodiment, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. In some embodiments, the control device 530 includes other interactions and implementations for grouping and ungrouping zones via the user interface 531. In certain embodiments, the representations of playback zones in the playback zone region 533 b can be dynamically updated as playback zone or zone group configurations are modified.

The playback status region 533 c includes graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 533 b and/or the playback queue region 533 d. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system 100 via the user interface 531.

The playback queue region 533 d includes graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device. In some embodiments, for example, a playlist can be added to a playback queue, in which information corresponding to each audio item in the playlist may be added to the playback queue. In some embodiments, audio items in a playback queue may be saved as a playlist. In certain embodiments, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In some embodiments, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items.

When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped.

FIG. 6 is a message flow diagram illustrating data exchanges between devices of the media playback system 100 (FIGS. 1A-1M).

At step 650 a, the media playback system 100 receives an indication of selected media content (e.g., one or more songs, albums, playlists, podcasts, videos, stations) via the control device 130 a. The selected media content can comprise, for example, media items stored locally on or more devices (e.g., the audio source 105 of FIG. 1C) connected to the media playback system and/or media items stored on one or more media service servers (one or more of the remote computing devices 106 of FIG. 1B). In response to receiving the indication of the selected media content, the control device 130 a transmits a message 651 a to the playback device 110 a (FIGS. 1A-1C) to add the selected media content to a playback queue on the playback device 110 a.

At step 650 b, the playback device 110 a receives the message 651 a and adds the selected media content to the playback queue for play back.

At step 650 c, the control device 130 a receives input corresponding to a command to play back the selected media content. In response to receiving the input corresponding to the command to play back the selected media content, the control device 130 a transmits a message 651 b to the playback device 110 a causing the playback device 110 a to play back the selected media content. In response to receiving the message 651 b, the playback device 110 a transmits a message 651 c to the computing device 106 a requesting the selected media content. The computing device 106 a, in response to receiving the message 651 c, transmits a message 651 d comprising data (e.g., audio data, video data, a URL, a URI) corresponding to the requested media content.

At step 650 d, the playback device 110 a receives the message 651 d with the data corresponding to the requested media content and plays back the associated media content.

At step 650 e, the playback device 110 a optionally causes one or more other devices to play back the selected media content. In one example, the playback device 110 a is one of a bonded zone of two or more players (FIG. 1M). The playback device 110 a can receive the selected media content and transmit all or a portion of the media content to other devices in the bonded zone. In another example, the playback device 110 a is a coordinator of a group and is configured to transmit and receive timing information from one or more other devices in the group. The other one or more devices in the group can receive the selected media content from the computing device 106 a, and begin playback of the selected media content in response to a message from the playback device 110 a such that all of the devices in the group play back the selected media content in synchrony.

IV. Power States in a Constant-Powered or Battery-Powered Playback Device

In some embodiments, an electronic device, such as a playback device 220 in accordance with an embodiment of the invention illustrated in FIG. 7, may have at least one battery 216 and/or a charging interface 218 that provide power to the playback device 220. Other components 211-212 j may be similar to those described further above with respect to the playback device 110 a illustrated in FIG. 1C.

The at least one battery 216 may be a rechargeable battery (e.g., a lithium-ion battery, a lithium-ion polymer battery, a lead-acid battery, a nickel cadmium battery, or a nickel metal hydride battery, among other examples) or a disposable battery. The charging interface 218 may receive power from an electrical outlet, an external battery, or an electromagnetic source (e.g., the charging interface 218 may be configured for inductive charging) to facilitate charging of the at least one battery 216. The charging interface 218 may be configured as a base on which the audio playback device may be placed to charge the at least one battery 216.

The playback device 220 may be a “battery-powered device” (or generally “battery-powered”) when it obtains power from the at least one battery 216. The playback device 220 may be a “constant-powered device” when it receive power via the charging interface 218 or directly from an electrical outlet (e.g., without charging an internal battery). Sets of power states may be defined for when the playback device is operating on battery power separately from when the playback device is plugged in or charging, or when the playback device is constant-powered. Different power states can define sets of conditions of components of the playback device as discussed below. A state diagram shown in FIG. 8 conceptually illustrates power states according to an embodiment of the invention. The states include: active, which may transition to standby or sleep; sleep, which may transition to active or sleep; and sleep, which may transition to active or standby. In other embodiments, certain of these transitions may be limited. Still further embodiments can include an “off” state that may be transitioned to or from another state.

In many embodiments of the invention, an active state involves components of the playback device being powered on and/or ready to receive instructions or media content and/or the playback device playing back media content. In certain embodiments, the playback device enters standby state from active state after a predetermined time (e.g., 2 minutes) of not playing back any content, e.g., playback is stopped or paused. In many embodiments, certain components related to producing sound from the audio components are powered down/off or in a standby/low power mode during standby state. In further embodiments, certain components related to receiving and/or processing data or messages from other devices over the network are powered on and/or in a ready state during the standby state.

In several embodiments, the playback device enters sleep state from standby state after a predetermined time (e.g., 15 to 60 minutes) of being in standby state. In many embodiments, certain components of a playback device, such as, but not limited to, any components of input/output 211 or electronics 212 illustrated in FIG. 7 and discussed further above, may be powered down/off or in a standby/low power mode during sleep state. In some embodiments, sleep state maintains the powered down/off or standby/low power mode of components in the standby state.

In further embodiments, certain components of the playback device may be powered on periodically during sleep state. For example, one or more of the components of analog I/O 211 a, digital I/O 211 b, and/or network interface 212 d may be powered down or in a standby/low power mode in sleep state and powered up for short periods of time (e.g., 300 ms) at predetermined time intervals to check for messages and/or listen for a wake up message (e.g., magic/wakeup frame). In different embodiments, various ways of waking the playback device (i.e., triggering a change from sleep state to standby or active state) can be events such as, but not limited to, activation of a hardware control on the playback device and/or a magic frame received over WiFi and/or NSF/BLE. Certain mechanisms of waking up a playback device may require the MAC address of a network interface on the playback device, such as the network interface 212 d of playback device 220. A table describing sample functions and behaviors that may be available to a playback device while in different power states in accordance with an embodiment of the invention are listed in Table 1 below.

Power State Function or Behavior Active When connected to the interne, can be targeted by direct control, voice services, and remote playback services (such as Airplay) Active or standby Transition to sleep state with short power button press Active, standby, or Transition to off with long power button press sleep Standby While on battery power, conserve power by e.g., step down CPU frequency Sleep Transition to active state by short power button press Sleep Transition to active state by Bluetooth wake-up message Sleep Transition to active state by voice command Active If woken by non-user initiated event, go back to sleep upon completion Off Transition to standby or active with power button press Off Transition to standby or active when charging battery and reaches battery minimum level Off Transition to standby or active when placed on charger Active or Standby Transition to sleep after a period of inactivity when battery powered Sleep Transition to off after a period of inactivity when battery powered

Techniques are discussed below for maintaining knowledge of the MAC address in one or more central repositories so that a message can be sent to the playback device when local devices, such as a local controller device, do not know that the MAC address is associated with the playback device. Although a specific implementation of playback device is discussed above with respect to FIG. 7, one skilled in the art will recognize that any of a variety of playback device configurations may be utilized in accordance with the invention as appropriate to a particular application.

Storing Device Address and State Information at a Repository

A waking device may not have the MAC address or other network address for a playback device that is in sleep state. In one example, the waking device may have previously received and temporarily stored the MAC address from the playback device but no longer has the information locally stored after a duration of not sending data to or receiving data from the playback device. In order to wake the playback device with a message using a MAC address, the waking device will need the MAC address of the playback device to which to send the wake-up message that has the magic frame. Therefore, it can be useful for a playback device to transmit its MAC address (or other network address) as well as optionally additional device information or state information to a central repository where a waking device may find it. For example, it can transmit the MAC address at an earlier time before transitioning to sleep state.

A process for sending and retrieving state information at a central repository in accordance with an embodiment of the invention is illustrated in FIG. 9. The process 900 can include switching (902) power states of a playback device, for example from active to standby or to sleep. The process 900 includes sending (904) a MAC address associated with the playback device (or one of its network interfaces), and optionally additional device information and/or state information, from the playback device to a central repository in connection with an event (e.g., changing power state or triggered by a set time interval). In many embodiments of the invention, the central repository is a cloud network or a server within a cloud network. Device information can include, but is not limited to, an associated user account, a device identifier, and/or a device serial number. State information can include, but is not limited to, a battery level of the device, a power source, group information, availability to respond to particular services or protocols (e.g., Apple Airplay), the state of the device (e.g., active, standby, sleep, power off), and/or a reason why the state and/or device information is being transmitted. For example, when the device is in BTLE (Bluetooth Low Energy) mode or powered off/down, it may not be able to receive or respond to magic frames.

In some embodiments, the state information is transmitted periodically. Additionally or alternatively, the state information is transmitted in connection with (e.g., soon prior to, simultaneously with, or soon after) certain power state changes/transitions of the playback device (e.g., removed from charger power to operate in battery mode, before entering sleep mode, before shutting down, when battery level reaches a lower threshold, and/or when disconnecting from the network).

A waking device attempting to discover available playback devices or connecting to a playback network after some period of time or for the first time may not have information on MAC addresses and/or state information for playback devices that it seeks to send communications to, e.g., wake-up messages or playback instructions. A waking device may be, for example, a controller or a second playback device that is part of a group or bonded zone with the sleeping playback device that is the recipient of the communications. As discussed further above, a waking device (e.g., controller device or group controller) may receive state information (e.g., directly or by broadcast) including the MAC address from each playback device within the local network (e.g., within a household) except from playback devices that are not currently able to send their MAC address. The waking device may use the information, for example, to display available devices on a menu in a user interface and/or to send a wake-up message or playback control message. For example, a playback command may be triggered by actuation of a user control on a second playback device that is part of a group or bonded zone with a first playback device, where the command relates to all playback devices in the group or zone (e.g., play a particular song or playlist). If the first playback device is in sleep state and the second playback device is not aware of the MAC address of the first playback device, the second playback device may request the MAC address from the central repository.

In some embodiments, a user interface of the waking device may display information relating to the playback device(s) that are not sending their MAC address, such as its current operating state, battery level, and/or a reason why the device is in the operating state it is in. In some cases, the displayed information may guide a user on how they can proceed with the playback device(s) not sending their MAC address, i.e. whether they can wake the playback device(s) to play back media content, or whether they should charge the playback device in the case the battery level of the playback(s) is low.

The process includes a waking device requesting and receiving (906) the playback device's MAC address and optionally any of the optional additional information associated with the playback device from the central repository. In some embodiments of the invention, the waking device is a controller having media playback system controller application software, such as the controller described further above with respect to FIG. 1H. In other embodiments, the waking device is a second playback device in a group or bonded zone together with the first playback device that is in sleep state, where the second playback device is designated as a group coordinator for the group or bonded zone. Techniques for specifying groups or bonded zones and a group coordinator are disclosed in U.S. Patent Publication No. 2017/0192739, incorporated by reference above. In various embodiments, the request may be for a specific playback device (e.g., by identifying the playback device), all available devices on the local network (e.g., by identifying the local network), all devices in a group or bonded zone (e.g., by identifying the group or bonded zone), and/or all devices associated with a user account (e.g., by identifying the user account). The request may make such identification, or the central repository may conclude such identification by the identification of the waking device.

In many embodiments of the invention, the waking device makes the requests of one or more MAC addresses of playback devices periodically, e.g., at predetermined intervals of time.

Using the playback device's MAC address, the waking device can send a wake-up message or other message to the playback device. In several embodiments, the wake-up message is sent in connection with a playback command, for example when instructing playback devices within a group to play the same content. The playback device can change (908) its power state based on the wake-up message, e.g., from sleep to active.

FIG. 10 is a message flow diagram illustrating data exchanges between devices of a media playback system according to an embodiment of the invention in a process similar to that discussed above with respect to FIG. 9. A playback device 1010 sends (1022) state information to cloud network or central repository 1024 based on an event, which may be triggered by, for example, a change in the power state (1020) of the playback device 1010 (e.g., from active or standby to sleep). A waking device 1012, which may be, for example, a controller device or a second playback device acting as group controller, sends (1024) a request for state information from the cloud network 1014. The request may be for a specific device, e.g., for playback device 1010, or may be for a specified group of devices, e.g., all playback devices on a user account or all playback devices on a local network. The cloud network 1014 returns (1026) state information for the requested devices. The waking device 1012 may generate (1028) a display of available devices based on the state location and/or may send (1030) a wake-up message to the playback device 1010. The playback device 1010 can respond to the wake-up message by changing power state (e.g., from sleep to active or to standby).

Although specific processes for maintaining device addressing information with a central repository is discussed above with respect to FIGS. 9 and 10, one skilled in the art will recognize that any of a number of processes or variations of the above process may be utilized in accordance with embodiments of the invention as appropriate to a particular application. In certain embodiments, the situation of the waking device not having the MAC address specific to each playback devices in the playback network may be addressed by the waking device broadcasting a general wake message to which each playback device is configured to transition from sleep to active or standby state and/or respond with its respective MAC address. This may result in the waking of every sleeping device.

V. Conclusion

The above discussions relating to playback devices, controller devices, playback zone configurations, and media content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods. Various cloud services/networks, playback devices, and/or waking devices may be utilized in accordance with embodiments of the invention to maintain knowledge of a MAC address or other network identifier for a particular playback device.

The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only ways) to implement such systems, methods, apparatus, and/or articles of manufacture.

Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of an invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the foregoing description of embodiments.

When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware. 

The invention claimed is:
 1. A method for maintaining knowledge of the network identity of a network-connected playback device while changing power states, the method comprising: maintaining a power state on a playback device, where the power state is in one power state of at least the states of: active, standby, and sleep; broadcasting a MAC address associated with the playback device at a first predetermined time interval when the playback device is in the active power state; broadcasting the MAC address associated with the playback device at a second predetermined time interval when the playback device is in the standby power state; determining that the playback device is entering a power state of sleep state; ceasing broadcasting the MAC address when the playback device enters the sleep state; sending state information from the playback device to a central data repository over a network responsive to the determination that the playback device is entering sleep state, where state information comprises a MAC address of the playback device; receiving the state information about the playback device by a waking device sent from the central data repository; waking the playback device periodically at predetermined time intervals while in sleep state to listen for messages addressed to the MAC address of the playback device; and receiving a wake-up message at the playback device from the waking device and responding by changing from sleep state to active state.
 2. The method of claim 1, further comprising: reducing power to at least one electrical component of the playback device when the playback device transitions from the active power state to the standby power state; and increasing power to the at least one electrical component of the playback device when the playback device transitions from the standby power state to the active power state.
 3. The method of claim 1, wherein the central data repository is a cloud network.
 4. The method of claim 1, further comprising sending a request for state information from the waking device to the cloud network, where the request for state information includes an identifier of the playback device.
 5. The method of claim 1, where the playback device is not connected to an external power source.
 6. The method of claim 1, where state information includes status of whether the playback device is in a state that cannot receive or respond to a magic frame.
 7. The method of claim 1, where the wake-up message is unicast addressed to the playback device.
 8. The method of claim 1, where the wake-up message is broadcast on a network that the playback device is connected to.
 9. The method of claim 1, requesting MAC addresses of all devices in a group of devices by a controller device, where the controller device and the playback device are members of the group of devices.
 10. The method of claim 1, where the second predetermined time interval is longer than the first predetermined time interval.
 11. The method of claim 1, wherein sending state information from the playback device to a cloud network when the playback device enters the sleep state comprises sending state information from the playback device to a cloud network when the playback device enters the sleep state from standby state.
 12. A method for changing power states of a network-connected playback device using a waking device, the method comprising: requesting and receiving, by a waking device from a central data repository over a network, state information about at least one playback device, where the state information includes a MAC address associated with each at least one playback device and data indicating that each at least one playback device is in a sleep state; receiving input on a user interface on the waking device causing an instruction to cause the at least one playback device to come out of sleep state; responsive to the input on the user interface causing the instruction to cause the at least one playback device to come out of sleep state, sending a wake up message from the waking device with a magic frame to each MAC address associated with each at least one playback device; maintaining a power state on a first playback device of the at least one playback device, where the power state is in one power state of at least the states of: active, standby, and sleep; broadcasting a MAC address associated with the first playback device at a first predetermined time interval when the first playback device is in the active power state; broadcasting the MAC address associated with the first playback device at a second predetermined time interval when the first playback device is in the standby power state; and ceasing broadcasting the MAC address when the first playback device enters the sleep state.
 13. The method of claim 12, where the input on a user interface on the waking device causing an instruction to cause the at least one playback device to come out of sleep state comprises detection of an input selecting the at least one playback device.
 14. The method of claim 12, where the input on a user interface on the waking device causing an instruction to cause the at least one playback device to come out of sleep state comprises an instruction to a group controller, where the group controller is a controller for a group of playback devices to which the at least one playback device belongs, to have the group of playback devices play a media content.
 15. The method of claim 12, where requesting and receiving, by a waking device from a central data repository over a network, state information about at least one playback device is performed periodically at a predetermined time interval.
 16. The method of claim 12, where requesting and receiving, by a waking device from a central data repository over a network, state information about at least one playback device is performed in response to an event on the waking device.
 17. The method of claim 16, where the event on the waking device comprises a controller application being opened on the waking device.
 18. The method of claim 16, where the event on the waking device comprises the waking device connecting to a local network containing the group of playback devices for the first time.
 19. The method of claim 12, wherein the central data repository is a cloud network. 